Description

The new release-order regression test hard-codes the full `python3 -m pip install build pytest
pytest-asyncio` command string, so non-semantic edits (adding pip flags, wrapping lines, or
reordering args) will fail CI even if dependencies are still installed before validation.

Code

packages/sdk/scripts/tests/release-order.test.mjs[R50-87]

+test('release workflows install Python SDK test dependencies before validation', async () => {
+  const installCommand = 'python3 -m pip install build pytest pytest-asyncio';
+
+  const releaseSdk = await readRepoFile('.github/workflows/release-sdk.yml');
+  const autoRelease = sectionBetween(
+    releaseSdk,
+    '  auto-release:',
+    '  sync-labs-agent:',
+    '.github/workflows/release-sdk.yml',
+  );
+  assertOrder(
+    autoRelease,
+    installCommand,
+    '- name: Run semantic-release',
+    '.github/workflows/release-sdk.yml auto-release',
+  );
+
+  const manualRelease = sectionBetween(
+    releaseSdk,
+    '  manual-release:',
+    '  testpypi-smoke:',
+    '.github/workflows/release-sdk.yml',
+  );
+  assertOrder(
+    manualRelease,
+    installCommand,
+    '- name: Validate SDK',
+    '.github/workflows/release-sdk.yml manual-release',
+  );
+
+  const stableRelease = await readRepoFile('.github/workflows/release-stable.yml');
+  assertOrder(
+    stableRelease,
+    installCommand,
+    '- name: Release stable packages (orchestrator)',
+    '.github/workflows/release-stable.yml',
+  );
+});

Relevance

⭐ Low

Repo’s release-order tests already hard-code exact workflow substrings; pattern merged unchanged in
PRs #2496 and #2908.

PR-#2496
PR-#2908

ⓘ Recommendations generated based on similar findings in past PRs

Evidence

The test defines a single exact installCommand string and uses assertOrder to require that exact
substring to appear before subsequent workflow steps, which will break if the command text changes
even when behavior is unchanged.

packages/sdk/scripts/tests/release-order.test.mjs[50-87]

Agent prompt

The issue below was found during a code review. Follow the provided context and guidance below and implement a solution

### Issue description
`release-order.test.mjs` asserts exact string equality on the full pip install command. This makes the test fragile: harmless changes to pip flags/formatting can break CI despite preserving the intended invariant (Python test deps installed before SDK validation paths).

### Issue Context
The intent is to enforce ordering (install deps before validation) and ensure the right tooling is present, not to enforce an exact command literal.

### Fix Focus Areas
- packages/sdk/scripts/__tests__/release-order.test.mjs[50-87]

### Suggested change
Update the test to assert more stable invariants, for example:
- Assert `- name: Install Python build and test tools` appears before the validation step(s) in the relevant workflow sections.
- Separately assert the section contains `python3 -m pip install` and contains `pytest` and `pytest-asyncio` (and `build` where needed), without requiring the full command string to match exactly.
This keeps the regression coverage while avoiding false failures on benign workflow refactors.

ⓘ Copy this prompt and use it to remediate the issue with your preferred AI generation tools